home *** CD-ROM | disk | FTP | other *** search
- Path: news.halcyon.com!usenet
- From: normanb@halcyon.com (Norm Bryar)
- Newsgroups: comp.lang.c++
- Subject: Re: Problems calling DLLs
- Date: Thu, 01 Feb 1996 16:25:02 GMT
- Organization: Northwest Nexus Inc.
- Message-ID: <4eqpg0$c9q@news.halcyon.com>
- References: <4enopb$hd8@kuikka.inet.fi>
- NNTP-Posting-Host: blv-pm2-ip25.halcyon.com
- X-Newsreader: Forte Free Agent 1.0.82
-
- Experiment with calling conventions, perhaps?
- Try __cdecl to force no decoration at all; __stdcall to append @N,
- where N is the byte-count of the argument list.
-
- If you have any library Toolbook does recognize, by all means,
- dumpbin /exports or dumpbin /symbolson the thing and look at how the
- names are represented. (This is a Visual C++ 2.x/4.0 util for Win32,
- probably Borland will have it or their own exehdr util or something).
-
- Hope this helps.
- --Norm
-
- asko.juvonen@caiproint.inet.fi (asko juvonen) wrote:
-
- >I have made some DLLs with Turbo C++ for Windows 4.5, but calling
- >programs are unable to find any functions in the DLLs, unless the
- >corresponding import library is linked to the program, after which
- >everything works fine. The problem is, the DLLs are ment to be used
- >with a Toolbook program, and AFAIK there is no way to link the
- >implibs with Toolbook. What can I do to make Toolbook see the
- >functions in my DLLs? Is there some particular style I should use
- >when defining functions? I currently use the extern "C" style,
- >resulting in case sensitive function names starting with an
- >underscore (no C++ name mangling).
-
-
-